Name of the BOM Group, which must be unique.

If clicked, displays the Features form, which is used to manage sales features applicable to this Category. Features, used in connection with the Deacom Product and Sales Configurator, are a group of similar options that may be chosen or configured based on different sales choices. 

Displays the name of the inventory category, which must be unique.

Displays the planned annual sales in dollars for this Category. This field is available for use in the Sales > Order Reporting Ranking report.

If checked, this record is active. Only active records may be used in the system.

If checked will provide the default entry when creating new inventory items. 

Select an appropriate Unit of Measure from the drop down list.

Numeric field used to define the minutes required to receive the Unit of Measure when receiving items in the specified Unit Of Measure that are assigned to this Category.

If clicked, opens the Edit Feature form and allows the user to select a Feature.

• The Endpoints or sub-Features within the Feature will be available to all Sub-Categories and items within the Category, unless overridden at those lower levels.
• Those overrides can remove Endpoints or sub-Features, but not add them, so all available Endpoints and Features should be defined at the Feature level and subtracted from the Feature tree at the appropriate Category, Sub-Category, or Item Master level.

If clicked, opens the Feature Overrides form, which displays a feature tree of this Category and all available options and prices, with the capability of overriding pricing and availability.

• Overrides established at the Category level are in effect at the Sub-Category and Item Master levels, unless overridden at those levels.
• Once an override is modified and saved, the new value from the Category level will be inherited to the Sub-Category and Item Master levels.

If clicked, opens the Feature Inclusions form, which displays a list of the inclusions and exclusions that have been added to the current Feature.

Displays the name of the selected Feature or Endpoint.

If checked, allows the user to modify the pre-defined Price of the selected Feature or Endpoint.

Only available when the "Override Price" flag is checked. Allows the user to define a new Price for the selected Feature or Endpoint.

If checked, allows the user to modify the availability of the selected Feature or Endpoint.

Only available when the "Override Status" flag is checked. Pick list used to modify the availability of the selected Feature or Endpoint. Options are:

• Available
• Default
• Unavailable

If checked, allows the user to edit the "Commissionable" flag of the selected Feature or Endpoint.

Only available when the "Override Commission" flag is checked. Allows the user to modify the selected Feature or Endpoint to be eligible for Commissions.

The date the override begins taking effect.

Enter appropriate number

Option to link a part number to the selected container. Only active part numbers with the "Unit Serialization" property checked will be displayed in the list.

• Used in situations where Containers will be assigned to Bills of Materials which allows visibility and tractability in MRP.

Select the appropriate Container unit.

Enter the appropriate tare weight for the selected Container. Tare weight represents the empty weight of the Container.

Enter the date the Container was acquired.

Enter cost at time of acquisition.

Pick list used to select the method with which depreciation costs are posted. Options are:

• None - A specific method is not used to reduce the carrying amount of a fixed asset.
• Straight Line - Generally used to gradually reduce the carrying amount of a fixed asset over its useful life. Designed to reflect the consumption pattern of the underlying asset, and is used when there is no particular pattern to the manner in which the asset is to be used over time. Usually the easiest method to calculate and therefor results in fewer errors.

Account to which depreciation charges will be credited. The corresponding entry is a debit to the "Depreciation Expense" account Accounting > Options.

Indicates the useful life, in months, for this Container.

Displays the current cost for this Container. This field will display the "Acquisition Cost" if "Depreciation" is set to "None". If set to "Straight Line", this field will display as a linear interpolation from the "Acquisition Cost" to zero, based on the "Acquired Date".

The name for the repair or maintenance task associated to the selected Container.

Pick list used in connection with the "Frequency" field to specify the unit of when maintenance will be performed on the Container. Options are:

• Calendar Days - Used in connection with the "Schedule Type", "Day Of", and "Day", the number listed in the "Frequency" field is the number of days on a calendar that will pass until maintenance must be completed.
• Hours Used - The number listed in the "Frequency" field is the number of hours the Container may be used until maintenance must be completed.
• Manual - Maintenance is not completed on a set schedule, but as the company/operators see fit. Selecting this option removes the ability to use the "Frequency" field.
• Metered - Used in connection with the "Meter Reading" flag and "Max Meter Reading" field on this form, the number listed in the "Frequency" field is the meter reading of when maintenance must be performed. A "Metered" task will be due immediately once the meter reading exceeds the Frequency.
• Quantity Produced - The number listed in the "Frequency" field is the number of units that may be produced on the selected Work Center until maintenance must be completed.

Provides the interval indicating how many days, hours, or how much usage is allowed between maintenance task completion.

Only used with a "Recurring Type" of "Calendar Days". Pick list used to specify the basis of how recurring maintenance tasks, based on the number of Calendar Days specified, will be rescheduled. Options are:

• Completion Date - Maintenance tasks will be scheduled based on the date a Maintenance Job was completed.
• Creation Date - Maintenance tasks will be scheduled based on the date a Maintenance Job was created.

For example, assume a maintenance task is set on the Maintenance tab of a Container with a "Recurring Type" of "Calendar Days", a "Frequency" of "7", and the "Schedule Type" is set to "Created Date". Assume a Maintenance Job is created on Monday, Sept 7th. If an MRO report is run, the "Due" column for this Maintenance task will be set to Monday, Sept 14th. Likewise, if the "Schedule Type" was set for "Completion Date" and the same Job was completed on Wednesday, Sept 9th, then running the MRO report would indicate that the "Due" column for this maintenance task would be set to Wednesday, Sept 16th.

Indicates the first date that the system should consider when scheduling maintenance for this Container. When a value is entered and MRO is run, if a Maintenance task has never had a Job finish against it, the system will use this date as the last Job finish date instead of an empty date. When a date is entered in this field, the "Last Date" in MRO gets updated with this same date. If no Jobs have been created for a Maintenance task with a "Recurring Type" of "Calendar Days" previously, then the Initial Date will be set as the "Initial Date" + "Frequency" days.

Only used with a "Recurring Type" of "Calendar Days" and used in conjunction with the "Day" field. Pick list used to indicate how the maintenance task due date should be snapped on a calendar when using MRO. Options are:

• Month - The maintenance task will be snapped to the "Day" indicated for the current month. For example, if "Day" is set to "3" and "Day Of" is set to "Month", the task will snap to the 3rd of the month on the calendar. If the day of the month is less than the current date, it would snap to the following month.
• None - The maintenance task does not snap based on calendar week or month.
• Week - The maintenance task will be snapped to the "Day" indicated for the current week. For example, if "Day" is set to "6" and "Day Of" is set to "Week", the task will snap to Saturday on the calendar. If the day of the week is less than the current date, it would snap to the following week.

Only used with a "Recurring Type" of "Calendar Days" and used in conjunction with the "Day Of" field. The value entered in this field indicates the specific day of the month or week (depending on the "Day Of" selection) that the MRO calendar will snap to when scheduling maintenance tasks. The system begins a week with Monday, so with "Day Of" set to "Week", a "Day" set to "1" represents Monday and a "Day" set to "7" represents Sunday.

Search field used to select the non-stock item that represents the maintenance or repair activity associated with the selected maintenance task.

Search field used to assign the maintenance task to a group. MRO Groups, managed via Production > Maintenance > MRO Groups allow maintenance tasks assigned to the same group to be placed together on the same Job when creating the Job via MRO.

Pick list used to select what impact this maintenance task will have on a machine's or location's availability. Options are:

• Facility - Used when performing the maintenance task will stop the ability to operate in the Facility to which the Work Center belongs.
• None - Used when performing the maintenance task permits the ability to operate as normal (no machinery or locations must be shut down or taken offline).
• Shop Area - Used when performing the maintenance task will stop the ability to operate in the Shop Area to which the Work Center belongs.
• Work Center - The default value, assuming that the Work Center cannot be used when performing the maintenance task (must be shut down or taken offline).

When Maintenance Jobs are scheduled for maintenance tasks that contain an "Unavailability Level" other than "None", the Master Production Calendar will black out the appropriate Work Centers, Shop Areas, and Facilities to indicate that they will be unavailable while maintenance is performed.

Used for scheduling purposes and to provide the default value when creating Maintenance Jobs via MRO. Tasks may be set with priorities starting from 1 to an unlimited number, with 1 being the highest priority and 5 being the default. If multiple tasks are set on one Container, the tasks are scheduled according to the value entered in their respective "Priority" fields.

Used in connection with the "Meter Reading" flag. Indicates the point at which the meter will roll over when entering meter readings on Job lines that include a Container with a recurring type of "Metered". This field allows the system to calculate the difference before the meter rolled over to estimate when the next reading should occur.

Search field used to copy any documents attached to the Container (via the "View Docs" button on the Edit Work Center form) over to MRO Jobs created for this maintenance task. The documents must belong to the selected Document Category (selected when initially attaching the documents to the Container) to be copied to the Job. The documents can be used as part of the batch ticket record for the Job and may be viewed via the "View Docs" button on the Job.

Memo field used to store additional details or instructions for IT/Dev/Support MRO tasks.

Displays the name of the Dangerous Good.

Enter appropriate number.

Memo field. The name required to ship a dangerous good. These names are pre-defined by US DOT and IATA. As a result, there can be different Proper Shipping Names for ground versus Air shipments. Proper Shipping Name must be EXACTLY what FedEx requires including capitalization and punctuation. The current best practice for this field is as follows: In instances where the Proper Shipping Name is different for ground versus air, add multiple Dangerous Good entries one for air, one for ground. On the package line detail, you can choose a different Dangerous Good option.

This field is the technical/chemical name of the specific item being shipped. This name should be on the item master and is the reason for the naming best practice listed above.

Pick list used to select the Hazard Class to which the good belongs.

• This selection is required for FedEx Hazardous Material shipping.
• For more information, refer to the FedEx site's Shipping Hazardous Materials page.

If a material contains a hazard in addition to the primary hazard, it is specified using this field.

• Per FedEx regulations, abbreviations and codes are not acceptable.

Choose the correct packing group associated with the dangerous good. Options are I, II, III, and None.

Search field used to select the necessary details regarding the packaging of dangerous goods for use with the FedEx integration.

• Options are maintained via Sales > Maintenance > Packing Instructions.
• Only FedEx Air shipments, not Ground, require Packing Instructions.
• The Ship Via form contains a "Packing Instructions Required" flag, which allows companies to control which shipping methods require instructions.
• When shipping hazardous materials, Packing Instructions are only required if the Ship Via "Packing Instructions Required" flag is set to true AND hazardous materials are in the shipment.
• The "Dangerous Goods" and "Packing Instructions" fields of the item being shipped are available to the Job Label and Bill of Lading reports.
  • The fields are: dn_name, dn_regnum, dn_shipname, dn_techname, dn_hazard, dn_packgroup, pi_name.

Long memo field used to store the details regarding the selected dangerous good. This field may be added to print outs associated with the shipment of dangerous goods in Deacom, such as the Bill of Loading.

• Added in version 17.04.006.

Displays the name of the Dock.

Search field used to select the Facility to which the Dock belongs.

Search field used to select the Facility Group to which the Dock belongs.

Pick list used to determine how the Dock will be used in the Facility specified. Options are:

• All - Indicates Dock will be used to both ship and receive orders.
• Receipts - Indicates Dock will be used to receive orders.
• Shipments - Indicates Dock will be used to ship orders.

Displays the name of the Facility, which must be unique.

First line of the Facility address.

Optional second line of the Facility address.

City, State, Zipcode, and Country of the Facility.

Primary phone number for the Facility.

• When using the FedEx option in Deacom, this field together with the Street, City, State, Zipcode, and Country Code are required.

Search field used to select a Country Code phone mask for the Facility, if required. 

Displays the GLN for the Facility, if required.

• 13 digit part of the GS1 systems of standards
• Is a simple tool used to identify a location and can identify locations uniquely where required.

Search field used to select a Currency other than the default that will be used to book transactions that occur for this Facility.

• Useful for scenarios in which Facilities may be located in different countries and therefore their home Currencies would differ and the Facility transactions should be booked in a foreign currency, including values for inventory, labor, burden, etc.
• In association with this option the following fields/features have been added in the system:
  • A read only "Currency" field on the Edit Facility Item > Costs tab for reference.
  • Currency conversion has been added to BOM roll-ups and all inventory transactions that use standard cost or transfer between Facilities.
  • Display warnings to alert users when posting to an account with a Currency different than the transaction Currency.
  • A "Currency" filter has been added to multiple reports in Inventory Reporting and Job Reporting and the reports have been enhanced to calculate in the specified Currency.

Displays the Facility facsimile machine number, if known.

Character text field. Displays the name of the individual to contact in case of an emergency.

Pick list used to select the conditions in which items purchased, produced, or sold in this Facility are allowed to go negative. This selection overrides the default selection on the Item Master General 1 tab. Options are:

• Always - Inventory is always allowed to go negative in this Facility, regardless of the setting on a Part's Item Master. If "Always" is selected, the inventory availability color on the Master Production Calendar will display as green, even when there is not enough inventory on hand.
• Follow Part - The "Negative Inventory" selection on the Item Master General 1 tab dictates how negative inventory is handled in this Facility.
• Never - Inventory is never allowed to go negative in this Facility, regardless of the setting on a Part's Item Master.
• Once - Items in this Facility are allowed to go negative once, but cannot go further negative until the situation is resolved and inventory changes to positive.

Search field used to select a Print Substitution Group for forms printed when this Facility is used. 

If checked, this record is active. Only active records may be used in the system.

If checked, the selected Facility will be defaulted whenever a transaction or record contains a "Facility" field.

If checked, inventory transactions other than physical inventory postings (such as issues, reserves, and moves) will be prevented from occurring for this Facility.

• This flag should be checked when performing physical inventories to ensure that no transactions occur between the time the inventory snapshot is taken and the time when the physical inventory worksheet is posted.
• If checked and a user attempts to perform an inventory transaction for this Facility, a system prompt will be displayed to prevent the transaction from occurring.
• This flag also exists on Item Master, Item Master Facility, Location Type, and Location records.
• Note: If the "Automatically Prevent Included Item Transactions" field on the Physical Inventory Forms form is checked, this prevents users from performing inventory transactions on all items, or facility-specific items, if a Facility is indicated on the form when performing a physical inventory or cycle count. The field allows companies to more quickly prevent inventory transactions then using the alternative option of checking the "Prevent Inventory Transaction" flag on the item master record, either individually, or via the Price Updates Excel feature.

Pick list used to select how inventory lots will be costed when received via Inter-Company Transfers into this Facility or when invoicing from this Facility when using Cross-Facility Orders.

For Inter-Company Transfers, the current lot cost of material being transferred is not automatically used to determine the cost of material that is received into the receiving Facility. For example, assume an item has a list price of $5.00 specified on the Item Master Costs 2 tab, but that there is inventory of this item in "Plant A" with a lot cost of $7.00. If the Facility tab of "Plant B" has a Markup Type of "List Plus $" and nothing is specified in the "Markup Factor" field, the lot of the transferred item will be costed at $5.00 and not $7.00 when lots of this item are transferred and received into "Plant B" via the use of an Inter-Company Transfer. Also, when receiving an Inter-Company Transfer using any Markup Type other than "Ship and Hold", the Invoice Date on the order will populate with the Receipt Date.

For Cross-Facility Orders, the Markup Type needs to be set on the invoicing Facility, and lots are costed when the Cross-Facility Order is shipped.

Options are:

• Cost Plus % - The lot cost plus the value specified in the "Markup Factor" field below.
• Current Price Minus % - The "Current Total" as listed on the part's Item Master Costs tab less the value specified in the "Markup Factor" field below.
• Current Price Plus $ - The "Current Total" as listed on the part's Item Master Costs tab plus the value specified in the "Markup Factor" field below.
• Dollars Per Unit - The value specified in the "Markup Factor" field below will be used for each part unit transferred.
• List Minus %
  • For Cross Facility Orders - The price as defined on the order less the value specified in the "Markup Factor" field below.
  • For Inter Company Transfers - The price as defined on the Item Master Field "List Sales Price" field less the value specified in the "Markup Factor" field below.
• List Plus $
  • For Cross Facility Orders - The price as defined on the order plus the value specified in the "Markup Factor" field below.
  • For Inter Company Transfers - The price as defined on the Item Master Field "List Sales Price" field plus the value specified in the "Markup Factor" field below.
• Ship and Hold - The lot cost of shipped inventory will be written off to the Cost of Goods sold account associated with the item master(s) Revenue account at the time of shipment.
• Transfer Cost - The "Transfer Cost" as defined in the "Transfer Cost Expression" field on the Sales 2 tab within in System > Options; or if that field is empty, the value in the "Transfer Cost" field on the part's Item Master Costs 2 tab. The "Transfer Cost Expression" on this form will take priority over the other two previously mentioned fields.

Defines the percentage or dollar amount that will be applied when receiving material on Inter-Company Transfers or shipping material via Cross-Facility Orders and using an "IC Xfer Markup Type" other than "Item Master Transfer Cost" or "Ship and Hold".

• A markup factor may be defined on both a Facility and a part's Item Master General 2 tab via the "IC Trans Markup %" field. If factors are set in both fields, both values will be added to the order price.
• A "Markup Factor" of 0% will transfer the material at cost.

Pick list used to allow or restrict reserving incremental inventory within this Facility while using WMS. Incremental reserving was added for customers that need the ability to track and report lots as they are issued incrementally in Deacom and not just the total "rolled up" amounts or issued materials/lots. For example, if a Sales Order requires 170 pounds of sugar, and sugar is handled in 50 pound bags, a user would stage three bags and 20 pounds of loose sugar in a container. For some customers, seeing the sugar listed as 170 pounds on the Sales Order is acceptable; other customers may have process controls that demand they track the exact containers and increments and thus would want 4 lines of sugar on the order for 50, 50, 50, and 20 pounds, respectively. Options are:

• Both - Inventory may be both incrementally reserved and staged.
• None - Inventory may not be incrementally reserved or staged.
• Reserve - Inventory may be incrementally reserved, but not staged.
• Staging - Inventory may be incrementally staged, but not reserved.

Pick list used to determine how multiple Lots of the same Part are handled when receiving material on an Inter-Company Transfer. Options are:

• Lot - Forces the user to receive each Lot of a Part individually. Example: If an Inter-Company Transfer is created for 1,000 units of Part A and 10 Lots of 100 are shipped, when receiving, the user must enter that they counted 100 of Lot 1, 100 of Lot 2, 100 of Lot 3, etc.
• Part - Defaults the amount to receive to the full amount of all Lots for the selected Part on the order. Example: If an Inter-Company Transfer is created for 1,000 units of Part A and 10 Lots of 100 are shipped, when receiving, the user may receive all 10 Lots totaling 1,000 units in one transaction.

If checked, Inter-Company Transfers sent to this Facility will be received automatically.

• Supports situations in which material needs to be put away in defined Locations when receiving. The logic checks the following:
  • The "Default Location" selected on the Facility assigned to the part's Item Master.
  • The "Default Location" on the part's Item Master General 1 tab.
  • The Location flagged as default for the Location Type flagged as default for the Facility selected on the order.
• A prompt will be displayed if this flag is checked but there is incorrect setup.

If checked, this Facility may receive material shipped on Inter-Company Transfers.

If checked for the receiving Facility on an Inter-Company Transfer, the system will keep the material in the same Location and Location Type as it originated from the shipping Facility. If the same Location and Location Type do not exist for the receiving Facility, the receiving Facility defaults will kick in.

• Useful in situations where customers need to support the "receipt" of items into a "customer owned" Facility, where materials will not physically move form their storage Location.

If checked, ensures the lot picker for a custom part automatically opens when reserving an ICT in Reserve SO in the Warehouse Management System. If the option is un-checked and an inter-company transfer has one or more stocked parts, the form defaults to the first part in the part list and a lot picker does not automatically open (similar behavior to reserving to a normal sales order). 

If checked, the quantities shipped from this Facility on Inter-Company Transfers, regular Sales Orders, and Cross-Facility Orders are automatically finished on the linked header or line Job.

• Useful in situations where a co-packer makes finished goods for customers. For example, the customer may ship components and raw materials to a co-packer several times per week, via Inter-Company Transfers. Once the co-packer assembles and ships the finished goods (via ICT) back to the original Facility, the system will automatically consume/backflush the components and raw materials on the corresponding Job, assuming the shipping Facility on the second ICT has this flag marked as true and a header or line Job linked.
• Requires the "Allow Inter-Co. Transfer To Facility" flag to be set to true.
• A Facility, Location Type, and Location representing the co-packer must exist.
• When shipping lot required items on ICTs and the Facility has this flag set to true, the system will generate a user lot for the material. Specifically, the system will gather linked Job lines and generate user lots for the lines then set the user lot variable on the order line to the value of the Job line's user lot with the same part id.

Sets the default value for the "Ship on Save" flag on the Reserve SO form in WMS.

• Allows users to ship the order once all inventory has been reserved and all information has been correctly entered.
• Only displayed when the Reserve SO form is accessed from the Ship Sales Order form in WMS.

If checked, the system will not require that a specific lot be selected when shipping Sales Orders from this Facility using the Direct Store Delivery application. Instead, the system will use FIFO rules to select the lots for lot tracked items.

Search field used to select a Bill-to Company, assuming this Facility represents a location where the Point of Sale application is used. When entering an order via POS, if the Bill-to selected is also specified in this field of a Facility, that Facility will automatically populate on the order. 

Search box for all active Credit Card Processors, to select which Processor should be used for this facility when calculating sales tax information. In terms of credit card processor hierarchy, this field overrides the System Default, but not the the Bill-To Company Override. The hierarchy is:

• System Default CC Processor (enabled via the "Default" flag on the Edit Credit Card Processor form.)
• Facility CC processor (this field)
• Bill-To Company CC processor, located in Sales > Customers > Modify Bill-To Company

This field was added to support companies that have different Merchant IDs in different Facilities.

Pick list that determines the default shipping quantity at the facility level, which takes priority over the System options but still below Item level. Options include:

• Follow Sales Options - Default. Will use the option set in Sales Options.
• As Reserved - Sets the "Ship" quantity to the quantity reserved to the Sales Order (which may be less than the quantity ordered) and backorders the remaining quantity.
• Full - System will apply either the full requirements or all of the item available based off of the set Location and Lot filters.
• Zero - Sets the default quantity to 0. Must be selected if shipping with FedEx. This is because users will in essence build the Package(s) while preparing the items for shipment and will need to determine, possibly by weighing, the quantity that will be placed in the Package(s) for shipment, according to the established FedEx parameters.

Example: An order for 2 or 3 boxes of chocolates which will require the users to begin with zero quantity then make and weigh the three packages prior to generating labels and completing the shipping process. Additional information on the FedEx process is available via Shipping with FedEx and UPS.

Note: The General 2 tab on the item master record also contains a Default Shipping Qty field. If the field in the item master is set to "Default," the system will use the Default Shipping Qty option set here in System Options. If the item master has a different setting than "Default," the system will use the specified option only when shipping sales orders containing that item.

If checked, the lot will be received into the facility at the current cost, with no markup added to the inventory value.

• The inventory value plus any markup will be posted to the revenue accounts on the order lines. This value will be posted to the markup account as a debit in order to balance the transactions.

If checked,  will switch the facility and ship to locations when using TaxJar AND the state on the facility/ship to are the same.

Pick list used to determine how lots issued to WIP Jobs, or moved to Shop Areas, will be relieved during production. Options are First Expired and First Issued.

• Useful in situations where the relief of materials during production needs to be in sequence with the actual physical consumption/use of materials. In other words, in situations where companies will use the materials based on the sequence of how they were physically delivered to the Job, whether issued or not.
• When set to "First Expired" and all other lot criteria are tied, the system will check the system lot before the user lot to determine the tie breaker.
• When Production Relief is set to First Issued, this is the hierarchy for lot relief.
  1. fi_type ("special" has highest priority, then "sale" and "job", then "sal-reserv", then everything else)
  2. If the part currently being relieved has “restrict job relief to shop area locations” set to TRUE, AND if any fi_loid are in shop locations, it gets higher priority
  3. fi_date
  4. fi_recdate
  5. fi_attrib1
  6. fi_attrib2
  7. fi_attrib3
  8. fi_expires
  9. fi_lotdate
• When Production Relief is set to First Expired, this is the hierarchy for lot relief.
  1. fi_type ("special" has highest priority, then "sale" and "job", then "sal-reserv", then everything else)
  2. if any fi_loid are in shop locations, it gets higher priority
  3. whether fi_expires is null or not (if fi_expires is not null, that lot has higher priority)
  4. fi_type (any type that is NOT "staging", "Reserved inventory", or "sal-reserv" gets higher priority)
  5. fi_expires
  6. fi_lotdate
  7. fi_attrib1
  8. fi_attrib2
  9. fi_attrib3
  10. fi_balance
  11. fi_lotnum
  12. fi_id

Pick list used to allow or restrict issuing incremental inventory within this Facility while using WMS. Incremental issuing was added for customers that need the ability to track and report lots as they are issued incrementally in Deacom and not just the total "rolled up" amounts or issued materials/lots. For example, if a Job requires 170 pounds of sugar, and sugar is handled in 50 pound bags, a user would stage three bags and 20 pounds of loose sugar in a container. For some customers, seeing the sugar listed as 170 pounds on the Job is acceptable; other customers may have process controls that demand they track the exact containers and increments and thus would want 4 lines of sugar on the Job for 50, 50, 50, and 20 pounds, respectively. Options are:

• Both - Inventory may be both incrementally issued and staged.
• Issue - Inventory may be incrementally issued, but not staged.
• None - Inventory may not be incrementally issued or staged.
• Staging - Inventory may be incrementally staged, but not issued.

Pick list used to determine how the system will populate the default issue quantity for this Facility, on issuing forms in the main application and WMS and in the "Quantity" field on the Inventory Final Staging form. Options are:

• Follow System Options (default setting) - the system will use the selection in the "Default Issue Quantity" field in Production > Options for jobs in this Facility.
• Full - the full remaining amount required by the job.
• Zero - issue quantity will default to zero.

Notes: If set to "Full", the system will apply either the full requirements or all of the item available based off the set Location/Lot filters. 

If checked, users will always be prompted with a yes/no prompt to confirm that they are over issuing/staging material on Jobs in this Facility.

• Checked by default.
• This flag applies to both the main application and WMS.
• Un-checking this flag is useful in situations where customers will always over issue, such as when issuing full pallet quantities.

If checked, users will only be able to select Operations specified on the Job's Routing when Logging On/Off Jobs in the WMS application and in the main application via the Production > Payroll Entry transaction.

If checked, users will always be prompted with a yes/no prompt to confirm that they are under issuing/staging material on Jobs in this Facility.

• This flag applies to both the main application and WMS.

Displays the name of the group.

If checked, this record is active. Only active records may be used in the system.

Displays the name of the Endpoint, which must be unique.

• Endpoints are displayed below the Feature to which they are attached, so it is not necessary to repeat the name of the Feature in the name of the Endpoint.

Used to store the default quantity of the selected Endpoint, which is usually 1, that will be added to the configuration when this Endpoint is selected.

Used to store the default sales price of the selected Endpoint.

Field used to dictate the suffix, up to 10 characters, that the Sales Configurator should use to build and link to part numbers.

• When selecting Endpoints with suffixes in the Sales Configurator, the "Part Structure" field displays the original part number with the selected suffixes appended. When the user saves the configuration, the system looks for a part number that matches the part structure and if it finds one, prompts the user to use that item instead of the Feature item.

Memo field used to store notes about the selected Endpoint, which will be copied into the resulting configuration on the Sales Order, if this Endpoint is selected.

If checked, this record is active. Only active records may be used in the system.

If checked, this record is considered an Endpoint, as opposed to a Feature.

If checked, the sales price of this Endpoint is subject to Commission calculation rules.

If checked, the sales price of this Endpoint is subject to modification by Deal Pricing rules.

• Cost Plus Margin Deal Types are not applicable to Endpoints since there are no costs directly associated with them.

If clicked, opens the Edit Option form, used to attach a specific Part Number directly to a Feature, and optionally mark it as default, when the use of multiple Endpoints is not necessary. Otherwise, Endpoints can be linked to Item Masters in a way that the selection of several Endpoints brings a single Item Master, and its Bill of Materials, into the configuration.

If clicked, opens a mover form used to add a collection of Features or Endpoints to the current Feature.

• The mover form will display all active Features and Endpoints except the current Feature and all previously included Features and Endpoints.
• Once all desired records have been moved to the right-hand side of the form, clicking "Continue" will close the mover form and add the selections to the current Feature.
• Options added in error may be removed using the "Delete" button on the Edit Feature form.

If clicked, displays a feature tree of the selected Feature and all attached options and prices, which can be printed or exported to Excel.

If clicked, opens the Feature Inclusions form, which displays a list of the inclusions and exclusions that have been added to the current Feature. More information is available in the Edit Inclusion/Exclusion form section below.

Displays the name of the Feature, which must be unique.

Used to store the default quantity of the selected Feature, which is usually 1, that will be added to the configuration when an Endpoint of this Feature is selected.

If checked, this record is active. Only active records may be used in the system.

If checked, this record is considered an Endpoint, as opposed to a Feature.

If checked, this Feature allows the selection of multiple Endpoints.

• Not normally checked as Endpoints within a Feature are typically mutually exclusive.
• Desirable in a list of miscellaneous or unrelated packages or options.

If checked, the sales prices of the Endpoints of this Feature are subject to Commission calculation rules.

If checked, the sales prices of the Endpoints of this Feature are subject to modification by Deal Pricing rules.

• Cost Plus Margin Deal Types are not applicable to Endpoints since there are no costs directly associated with them.

If checked, the sales price of this Endpoint is available as a basis for Promotions calculations.

Pick list used to select the Parent-level Feature. Options include the sub-Features that are a part of the current Feature (all records with a value of "No" in the "EndPoint" column of the Edit Feature form).

Pick list used to select the Parent-level Endpoint. Options include the Endpoints that are a part of the sub-Feature selected in the "Parent Feature" pick list.

Pick list used to select the Child-level Feature. Options include the sub-Features that are a part of the current Feature (all records with a value of "No" in the "EndPoint" column of the Edit Feature form).

Pick list used to select the Child-level Endpoint. Options include the Endpoints that are a part of the sub-Feature selected in the "Child Feature" pick list.

If checked, this record is handled as an Exclusion.

• When a user is building a Sales Order and selects the Endpoint defined in the "Parent Value" field, the Endpoint defined in the "Child Value" field will be prevented from also being selected on the same order.

If not checked, this record is handled as an Inclusion.

• When a user is building a Sales Order and selects the Endpoint defined in the "Parent Value" field, the Endpoint defined in the "Child Value" field will automatically be added to the same order.

The Name of the Formulator or responsible department, which must be unique.

If checked, this record is active. Only active records may be used in the system.

If clicked, opens the Edit Document Entry form, used to add a new picture record.

If clicked, opens the Edit Document Entry form, used to modify the selected record.

If clicked, deletes the selected record.

If clicked, opens the picture selected.

Search field that opens a file explorer used to select the item picture. Displays the actual name of the image.

Displays a description of the image.

Search field used to select the appropriate Document Category for the item picture.

Displays the name of the Item Planner, which must be unique.

If checked, this record is active. Only active records may be used in the system.

Displays the name of the option, which must be unique.

If checked, this record is active. Only active records may be used in the system.

If checked, the selected option is the default for the "Item Search 1-5" fields on the User Fields tab when adding new Parts via Item Master.

Defines the name of the Location Type, which must be unique.

Pick list used to set negative inventory options this level. Options are: Always, Follow Part, Never, Once.

• This setting at the Location Type level takes precedence over the "Negative Inventory" setting on the Facility and Part, unless it is set to "Follow Part".
• Useful for situations in which customers need the ability to turn off negative inventory by Facility, but still keep it on at the Location Type/Location level.
• If customers are using strict lot control, allowing items to go negative is not advisable.

Search field used to select the Facility to which this Location Type will belong. When changing the Location Type's Facility on this form and saving the form, the system will check to see if there is any inventory with the location type still associated to it. If there is, the system will display the following prompt: "This location type cannot change facilities while there is still inventory associated with it."

If checked, this record is active. Only active records may be used in the system.

If checked, this Location Type will populate when the Facility selected in the field above is identified on forms requiring a Location Type. 

Displays the name of the Location, which must be unique.

• A blank value for location is not allowed, but the use of the name “None” is valid.

Displays a description of the Location.

Search field used to select the Location Type to which this Location belongs.

• Multiple Locations may be linked to one Location Type.

Search field used to define the Unit used to measure the Capacity quantity, with the most common usage being cubic feet.

• Used in connection with the "Capacity" field to support Directed Put Away.

Defines the maximum quantity of inventory that the Location can hold.

• Used in connection with the "Capacity Unit" field to support Directed Put Away.

Used in conjunction with Movement Rules to dictate when a Location is considered for replenishment. Priority for Location replenishment is determined by the sort rules on the rule used.

Determines the sequence the system will use when determining where material should be placed or selected from when issuing.

• The sequence is used to determine where material should be placed when used in connection with the "Putaway" function in the WMS application. Putaway logic: Once the "Putaway" button is clicked, the system will start with the default Location on the Item Master to see if there is enough space in that Location to store the Lot. If there is not enough room, the system will check each Location beginning with the next "Location Sequence" number listed after the default Location. Example: If the default Location has a "Location Sequence" of 50 and there is not enough room, the system will look for a "Location Sequence" of 51 and so on until a Location with sufficient room is found.
• The sequence is used to determine where to select material from when using the Location Priority optimize option on the Issue/Reserve form. When using this option the system optimizes lots by finding the first expiring lot for each part in each Location, beginning with the Location that has the lowest "Location Sequence" value.

Displays the date that inventory in this Location was last counted, via the posting of a Physical Inventory Worksheet, at any Facility, regardless of how many Facilities may be linked via the Item Master Facilities tab.

• The inventory/lots that were counted is based on how the Physical Inventory Worksheet was filtered and then posted. It does not necessarily indicate that all inventory lots in this Location were counted on the date indicated.

If checked, this record is active. Only active records may be used in the system.

• After inactivating Locations, have the scanner users log out then back in to Deacom to refresh the Locations available for use.

If checked, this Location will be default for the Location Type specified. This default will populate when the appropriate Location Type is identified on forms requiring a Location entry. 

Displays the name of the MRP Group

Displays the name of the Part Exclusion, which must be unique.

Allows the user to use a previously created Put Away Rule as a base for a new one.

Pick list used to determine to what the rule applies. Options are:

• All Part Numbers - Rule applies to all Parts.
• Category - Rule applies to all Parts that belong to the selected Category.
• Part Number - Rule applies to the selected Part Number.
• Item Search 1-5 - Rule applies to the selected Item Search value.
• Sub-Category - Rule applies to all Parts that belong to the selected Sub-Category.

Search field used to select the applicable Category, Part Number, Sub-Category or Item Search 1-5 that this rule applies to.

• Field caption changes based on the "For Type" selected.

Pick list used to determine where the rule applies.

• All Locations - Rule applies to all Locations.
• Facility - Rule applies to the selected Facility.
• Location - Rule applies to the selected Location.
• Location Type - Rule applies to the selected Location Type.

Search field used to select the applicable Facility, Location, or Location Type that this rule applies to.

• Field caption changes based on the "To Type" selected.

Pick list used to determine if the rule is subject to a specific capacity, and if so whether the capacity limit is amount from location, a specific absolute amount for this rule, or a percentage of total location maximum capacity.

• Amount - The material being received/moved may only occupy the amount of space specified by the "Capacity" field on this form, which is measured in the "Capacity Unit" specified on this form.
• From Location - The material being received/moved may only occupy the "Capacity" defined on the record of the Location the material is being moved from.
• None - The material being received/moved is not subject to a specific capacity.
• Percent - The material being received/moved may only occupy a percent, as specified by the "Capacity" field on this form, of the "Capacity" defined on the record of the Location to where it is being received/moved.

The Unit in which the "Capacity" is measured, when "Capacity Type" is set to "Amount".

The specific absolute amount or percentage of total location maximum capacity that may be consumed by the material.

If checked, this record is active. Only active records may be used in the system.

If checked, the system will look for and suggest to fill a location that meets both of the two criteria below.

• Location that already has inventory that matches the Put Away Rule criteria.
• Location that has capacity

In this case, the system will attempt to fill the location to capacity before trying to fill closer locations. This flag is unchecked by default.

Pick list used to determine how Locations are sorted when the system is iterating through the options to suggest one for use. Options are:

• Ascending - Locations are evaluated in ascending order based on the Location Sequence defined in the rule (e.g. [start], [start] + 1, [start] + 2, etc.). When highest Location is reached, wrap back to lowest Location and keep checking until all checked.
• Closest - Locations are evaluated in order using the Location Sequence defined in the rule and based on which one is closest to the starting Location (e.g. [start], [start] - 1, [start] + 1, [start] - 2, [start + 2], [start -3], etc.).
• Descending - Locations are evaluated in descending order based on the Location Sequence defined in the rule (e.g. [start], [start] - 1, [start] - 2, etc.). When lowest Location is reached, wrap back to highest Location and keep checking until all checked.

Pick list used to determine if the material being received/moved can be mixed in with other Parts, or segregated based on Category, Sub-Category, etc. Options are:

• Any Parts - The destination Location may contain any Parts.
• None - The destination Location must be empty.
• Same Category - The destination Location may only contain Parts that belong to the same Category as the Part being received/moved, as defined on the Part's Item Master General 1 tab.
• Same Part - The destination Location may only contain the same Part that is being received/moved.
• Same Sub-Category - The destination Location may only contain Parts that belong to the same Sub-Category as the Part being received/moved, as defined on the Part's Item Master General 1 tab.

Pick list used to determine if the material being received/moved can be mixed in with material classified as a different Inventory segment. Options are:

• All - The destination Location may contain material in any inventory segment (Inventory, Quarantine, Staging, etc.).
• Same - The destination Location may only contain material that is classified in the same inventory segment as the material being received/moved.

Pick list used to determine if the material being received/moved can be mixed in with material classified as a different QC status. Options are:

• All - The destination Location may contain material in any QC status (Approved, At-Risk, Pending QC, etc.).
• Same - The destination Location may only contain material that is classified in the same QC status as the material being received/moved.

Pick list used to determine if the material being received/moved can be mixed in with material labeled with a different Lot Number. Options are:

• All - The destination Location may contain multiple Lots of material with varying Lot Numbers.
• Same - The destination Location may only contain material that is labeled with the same Lot Number.

Allows the user to copy an existing Quality Control Group to use as a base for the one being created.

• Used Field values, if present, will be copied to the newly created Quality Control Group.

Opens the Edit Quality Control Item form, which is used to add a Quality Control Test to the group and assign values and other qualities.

Opens the Edit Quality Control Item form, which is used to modify the selected Quality Control Test.

Deletes the currently selected Quality Control Test.

Defines the name of the group.

Indicates the number of days after production that QC entry is allowed.

Pick list used to indicate when and how approval is required. Options are:

• All - Approval is required for all tests in the group, regardless if the tests are within range, passed, or failed.
• Failed - Approval is required only when tests in the group fail the testing parameters.
• None - Approval is not required for this group.

Approval overrides failed tests that are flagged as “Must Pass QC To Continue”. Rejection sends material into Failed QC status, where only approved users have access to it.

Pick list used to indicate when and how E-Signatures are required. Introduced in 15.03.072 and replaces the "Require E-Signature For Approval" flag. Options are:

• All - An E-Signature is required for all tests in the group, regardless if the tests are within range, passed, or failed. Only available when "Approval Type" is set to "All".
• Failed - An E-Signature is required only when tests in the group fail the testing parameters. Only available when "Approval Type" is set to "All" or "Failed".
• None - An E-Signature is not required for this group.

Only used when approving QC to determine how many e-signatures are required. Option to require, and store, multiple e-signatures when approving QC. If the number in this field is greater than 1, the system will display a signature form, requiring an entry, for the number specified in this field.

• Only enabled when the E-Sig Approval Type is not set to "None:.
• Text field with a mask of "9"
• When the E-Sig Approval Type is set to All or Failed, the value is this field will default to 1.
• Business Case: - useful for tight quality control processes where an employee and supervisor e-signature is required on QC results.
• Notes:
  • If multiple e-signatures are required, all must be completed, or no e-signature's will be entered/stored in the system.

  • The enforcement of different credentials per QC Group only is applied when the value in this field is greater than 1. So, for example: If approving quality control results, and there are two QC groups involved, each with an Approval E-Signature Count of "1" in this field, the same approver credentials can be used to sign off on each QC Group.

Used to determine how many e-signatures are needed to enter results. 

• Enabled only when 'Require E-Signature For Results' is true.

If checked, this record is active. Only active records may be used in the system.

This flag is not used for Quality Control Groups and therefore has no purpose if checked. It is listed only because it is a standard field on forms.

If checked, the system will complete empty tests with empty values and move them to QC list/values form. If not checked, the system will only move tests that have values to the QC list/values form.

• Checking this flag is useful in situations where QC will be performed incrementally on Jobs since users will be able to enter QC via the Close/Relieve form without having to go back to the first pass of QC results and enter values for tests not completed in that pass.

If checked, a valid Deacom username and password is required to be entered before the “Finish QC” step is allowed.

• Replaced with the "E-Sig Approval Type" pick list.
• A record of this approval is stored in Deacom in an encrypted record (AES-256 encryption like the rest of the system).
• The Deacom  application complies with the FDA requirement (21 CFR 11) for E-Signatures by employing at least two distinct identification components, namely a username and password as indicated in 21 CRF 11.200.
• If checked, the "Approval Type" field will automatically be set to "All".
• If results for a test with this flag checked are entered then modified, the user will be prompted to add a new e-signature for the modified results.

If checked, a valid Deacom username and password is required to be entered when applying each pass of QC results.

• A record of this approval is stored in Deacom in an encrypted record (AES-256 encryption like the rest of the system).
• The Deacom application complies with the FDA requirement (21 CFR 11) for E-Signatures by employing at least two distinct identification components, namely a username and password as indicated in 21 CRF 11.200.
• If checked, the "Approval Type" field will automatically be set to "All".

If checked, QC is performed after production.

• Valid only for groups pertaining to produced, not purchased material.
• Finished material is put into QC Hold status, pending test results.

If checked, approval is required for the QC results to be posted.

If checked, and the “Retain QC” field on the Vendor's General tab is set to “Same Part” or “All”, then the system will automatically populate the QC results when receiving the sameUser Lot for items from this Vendor.

• Useful in situations where companies trust the Vendor's products and QC process.
• Example: Assume a Vendor has "Retain QC" set to "Same Part" and the QC group has this flag checked. Part 123 is received with a Vendor Lot of "ABC" today and the same item and Lot is also received tomorrow. The user will be prompted to copy QC results when the “Receive” button is clicked on the PO. Once this happens, the Lot goes right into inventory and by-passes QC. The user can still choose a Location in inventory if it is not retained.
• The security option "Purchasing -- Select lots when copying QC" works with this feature. When set to no, the system will not show the lot selection mover form when copying QC results. This option is useful in situations where customers do not want the employees receiving the product to be making the decision on what QC values to copy.
• Systematically, if this flag is checked and
  • The QC Group is set on the Item Master, the copy vendor QC functionality will be used.
  • The "Do QC After Production" flag is not checked, and the QC Group is set on the Formula, the copy pre-production QC functionality will be used.
  • The "Do QC After Production" flag is checked, and the QC Group is set on the Formula, QC will not be copied since it is occurring after production.
  • The "Do QC After Production" flag is checked, and the QC Group is set on the Item Master, the copy vendor QC functionality will be used.
• Additional requirements that are supported by checking or not checking this flag:
  • Check this flag for products when, once QC approves the job (right labels, containers, etc.) the production team can finish as many pallets as needed.
  • Uncheck this flag for products when every single finish/pallet needs its own in-process QC approval before being finished. Another option for QC release of individual pallets is post-production QC.

Search field used to select a Quality Control Test to add to the group.

Search field used to select the Quality Control Security Group that applies to this test.

Displays a description of the test, up to 200 characters.

Memo field used to indicate the target value for the test.

• Both numeric and non-numeric test results are allowed.
• Maximum length is 120 characters.

Optional, set the default QC Test value in a QC Test setup which will populate by default. Useful if have many simple/optional QC Tests to lessen the burden of entry.

Indicates the minimum accepted value for the test. 

Indicates the maximum accepted value for the test.

Indicates the default value for a minimum detectable reading, generally used for legal requirements.

• Testers can indicate an amount was evident but below the stated detectable level for the test, the testing equipment, or both when entering QC results.

Field used for formatting the QC results on forms. When the Print Mask is not used, the Input Mask will be the fallback field used for formatting the QC Results on forms. Input Mask and Print Mask can be used together when users should enter results with 4 decimals, but only display 3 decimals. 

• Example: If results should always be displayed with 3 decimals, the value in this field should be “9.999”.

Defines the mask, which governs the format, that will be used when entering the results.

• Example: If results should always be 4 digits long, the value in this field should be "9999".

Pick list used to select which QC value, when multiple iterations of a test are performed, will populate on Part Forms. Options are:

• Average - The average of all values entered for this test will be used.
• Last - Most commonly used. The last value entered for this test will be used.
• Max - The highest value entered for this test will be used.
• Min - The lowest value entered for this test will be used.

Memo field used to store notes regarding the test.

• Notes will be retained when shipping and receiving an Inter-Company Transfer.

If checked, a value must be entered for this test prior to moving the item to inventory.

• This flag indicates that a value must be entered; it does not indicate that the value entered must be a passing value.
• This means that the validation that all required tests have been completed occurs for pre-production QC at the time of a finish.
• For post production QC, the validation occurs when the results are finished via Production > QC Result Entry.

If checked, a value entered for this test must be between the minimum and maximum defined.

• For tests set with a minimum but no maximum, results will pass if the result is greater than the minimum and the maximum is set to 0.

If checked, the test description, values, and notes will be available for display on Part Forms, including Certificates of Analysis.

• When checked, the "Required" and "Must Pass QC To Continue" flags will usually also be checked since Certificates of Analysis will primarily display required tests with passing results indicated.

If checked, the test description, values, and notes will be available for display on Purchase Orders.

• This allows companies to display/communicate the QC parameters that will be utilized.
• Even if this flag is checked, the appropriate fields will still need to be added to the appropriate Part Forms and Report Layouts in the system.

Displays the name of the security group.

If checked, this record is active. Only active records may be used in the system.

Displays the name of the test.

Describes the approved method to be used for conducting the test.

Indicates the Unit used to measure test results. 

Defines the mask, which governs the format, that will be used when entering the results. Note: The value entered in this field will provide the default to "Input Mask" field on the Edit Quality Control Item form when adding this QC Test to a Quality Control Group.

• Example: If results should always be 4 digits long, the value in this field should be "9999".

Field used for formatting the QC results on forms. When the Print Mask is not used, the Input Mask will be the fallback field used for formatting the QC Results on forms. Input Mask and Print Mask can be used together when users should enter results with 4 decimals, but only display 3 decimals. Note: The value entered in this field will provide the default to "Print Mask" field on the Edit Quality Control Item form when adding this QC Test to a Quality Control Group. 

• Example: If results should always be displayed with 3 decimals, the value in this field should be “9.999”.

Option to have the system compare the values for the selected criteria in this field on lots being relived to production jobs and transfer those values to the lot produced on the job. Options are None, Weighted Average, Average, Minimum, and Maximum.

• The QC Tests and QC Groups on the lots being relived must match those of the lot being produced.
• Business Case: Designed for blended lot scenarios where a lot produced on a job uses/relives multiple lots of the same material that is produced on the job and previously entered QC values can be transferred to the finished lot. The feature works for lots that are set to go into a "Pending QC" status during job finishing.

Name of adjustment reason, which must be unique.

Search field used to define an adjustment account for the selected reason.

• If an account is entered in this field, the system will use this account instead of the selected item's adjustment account when selecting this reason.
• This account applies when adjusting, not moving, inventory in the system.

If checked, this record is active. Only active records may be used in the system.

Opens the Edit Routing Sequence form, which is used add a Sequence to the Routing.

Opens the Edit Routing Sequence form, which is used to modify the details of the selected Sequence.

Deletes the selected Sequence from the Routing.

Allows the user to sort the order of the Sequences for this Routing.

Allows the user to copy an existing Routing as a starting point, which can then be modified and saved as a new Routing.

Allows the user to copy the currently selected Routing Sequence.

• The new Sequence will initially be added to the bottom of the list, but may be sorted as desired.
• The Edit Routing Sequence form will automatically be opened to modify or confirm the information for the newly created Sequence.

Displays the name of the Routing, which must be unique.

Indicates the typical number of units produced using this Routing.

Indicates the Facility for which this Routing is used.

If checked, this record is active. Only active records may be used in the system.

If checked, and "Inventory Costing" in System > Options > Inventory tab is set to "Standard Cost" or "FIFO Cost", labor and burden postings are re-calculated based on the Job's planned quantity (lj_planquant) as opposed to the batch size entered on the routing.

• Allows a Routing to be setup with no Batch size, then when selected on a Job, scale to the Job quantity and appropriately relieve the Operation costs evenly, regardless of the amount of finishes being performed.
• The formula with this flag checked should be the sum of the costs for each Sequence, calculated as follows:
  • For Sequences that are not flagged as "Batch": Operation rate + Work Center rate * Sequence Workers * Sequence Hours / Sequence Units * amount of Part that was planned.
  • For Sequences that are flagged as "Batch": Operation rate + Work Center rate * Sequence Hours * Sequence Workers.
• Jobs that do not have Routings will have labor costs equal to the Item Master accounting labor cost times the amount produced.

If checked, the system will adhere to the values on this record when this Routing is selected on Jobs when running MRP.

Used in conjunction with the "Split MRP Jobs By Job Quantity" flag on the Item Master Properties tab to define the default minimum batch size, in Stock Units, for produced materials.

• If the "Split MRP Jobs By Job Quantity" flag is not checked, this value will not be enforced.
• If a quantity is entered below the value defined in this field, a prompt will appear asking the user if they wish to continue.
• Users with the security setting "Jobs -- allow quantities less than job minimum" will be permitted to enter non-incremental quantities on Jobs.

Used in conjunction with the "Split MRP Jobs By Job Quantity" flag on the Item Master Properties tab to define the default maximum batch size, in Stock Units, for produced materials.

• If the "Split MRP Jobs By Job Quantity" flag is not checked, this value will still be enforced.
• If a quantity is entered above the value defined in this field, a prompt will appear asking the user if they wish to continue.
• Users with the security setting "Jobs -- allow quantities greater than job maximum" will be permitted to enter non-incremental quantities on Jobs.
• If the "Use MRP Settings" flag is unchecked, the Job Maximum field in Item Master will be used instead in a Work Center Capacity Report.

Search field used to select the Operation, which supplies the standard hourly labor cost, for which this Routing is used.

• Each Operation has a separate GL account for posting labor and overtime expenses.

Pick list used to determine if the selected Operation should be restricted when a user attempts to manually modify the Work Center on a Job Routing Step from the Job header. Options are:

• None - User is allowed to select from a list of all Work Centers.
• Work Center - User is only allowed to select from the list of Work Centers directly attached to the Routing Step.
• Work Center Type - User is allowed to select from a list of all Work Centers that have the same Work Center Type as any of the Work Centers attached to the Routing Step.

Defines how many outputs or pieces will be completed by the Operation in the time specified in the Hours field. If the "Batch" flag is set, this field will be grayed out.

Defines the amount of time required to complete the Operation. If the "Batch" flag is set, this operation will take the same amount of time for all jobs. Batch size or job size will not be considered.

Defines the number of Workers required to complete all Units within the Hours entered on the Sequence.

• This field may contain up to two decimals.
• This field is not required by the Deacom system but may be required based on individual customer requirements and SOPs.

Pick list used to dictate if the "Lead Time" will be based on the Start or End of the Job.

Used in conjunction with the "Lead Time Based On" selection and the Master Production Calendar to indicate the lead time, in hours, for this Sequence.

• Example: Assume there is Job with a "Planned Start" date of Jan 12 and one of the Job's Routing steps has a three day Lead Time (represented in hours). The system will indicate a "Due" date of Jan 15 on the Routing Calendar Detail form for this Job Routing Sequence.
• Decimals and negative numbers are not permitted in this field.
• If the "Schedule Continuously" check box on the General tab of the Routing form is checked, this field will be grayed out and unavailable for entry and the entry in this field, if set, will be reset to "0".

If checked, the Work Center using this routing sequence on the Master Production Calendar will be unavailable for scheduling based on where and when Operations on subsequent sequences occur. 

Memo field used to store processing notes specific to this Sequence.

Used to indicate if the Operation being performed takes a set amount of time regardless of the "Batch Size" defined on the Routing.

• When calculating labor cost
  • If checked, the system will divide the "Hours" specified on the General tab by the "Batch Size" on the Routing.
  • If checked, the "Units" field on the Edit Routing and Edit Routing Sequence forms will be grayed out.
  • If not checked, the system will use the normal calculation of "Hours" divided by "Units".
    • Example: Cleaning a machine after use takes 1.5 hours regardless of the "Batch Size".

Used to indicate if this Routing Sequence is a finishing step.

• When finishing Job lines, labor and burden costs for the sequences flagged as "Finishing" are totaled separately and stored in the new "Finishing Labor" and "Finishing Burden" columns available to the Job Reporting "Job Cost Detail" report.
• Useful for customers looking for more labor tracking detail in the "Job Cost Detail" report.

Checked by default. When checked, routing sequences will be scheduled on the Master Production Calendar over non-maintenance blackouts. Routing sequences will be scheduled to start before a blackout and then continue thereafter.

• The "Process Jobs Over Non-Maintenance Blackouts" field in Production > Options must be checked in order to use this field.
• If this field is unchecked, the system will either move the sequences forward or backward on the calendar depending on the scheduling method and continuous logic below:
  • If any sequence on the routing is unable to be scheduled without crossing a blackout/unavailability period the system will not schedule the entire job.
  • When manually re-scheduling an already scheduled sequence or placing a sequence on the calendar from the list of sequences in the bottom grid of the calendar, and the user places the sequence in a spot that would result in crossing a blackout/unavailability period, the following prompt: "This sequence can't be scheduled across scheduled across black outs." will be display and the system will put the sequence back where it was, and not move any others.
  • When manually re-scheduling a sequence to a valid Work Center and the user answer yes to move earlier/later/unscheduled sequences the system will check the setting in this field to ensure schedule around blackout setting is considered.
• Added in version 17.02.010.0000.

Used to indicate if the sequence is susceptible to the Optimize function in the Master Production Calendar. Defaults to True. When set to False, the selected sequence will remain in its initially scheduled time even if the Optimize function is used. 

When checked, all machine, labor, piece, etc. costs will be set to zero and not appear in any labor cost roll ups.

Search field used to select the Work Center, typically a specific machine within a given Shop Area, to which this Routing and the values below apply.

• Only Work Centers with Shop Areas that belong to the Facility selected on the Edit Routing form will appear in the list as available to select.
• Min Job Line Qty and Max Job Line Qty are available to set on the Work Center.

Defines how many outputs or pieces are needed to complete the Operation for the selected Work Center. If the "Batch" flag is set, this field will be grayed out.

Defines the amount of time required to complete all Units for the selected Work Center.

Defines the number of Workers required to complete all Units within the Hours entered on the Sequence for the selected Work Center.

• This field may contain up to two decimals.
• This field is not required by the Deacom system but may be required based on individual customer requirements and SOPs.

Pick list used to dictate if the "Lead Time" will be based on the Start or End of the Job.

Used in conjunction with the "Lead Time Based On" selection and the Master Production Calendar to indicate the lead time, in hours, for this Sequence for the selected Work Center.

• Users can schedule overlapping Routing Sequences within the same Work Center. See Scheduling overlapping Routing Sequences for more information.
• Users can schedule concurrent Routing Sequences for different Work Centers. See Scheduling concurrent Routing Sequences for more information.
• Decimals and negative numbers are not permitted in this field.

Memo field used to store processing notes specific to this Sequence for the selected Work Center.

If checked, will inherit the units, hours and crew size from the values on the General tab.

Defines the name of the schedule sequencer.

If checked, this record is active. Only active records may be used in the system.

If clicked, displays the Features form, which is used to manage sales features applicable to this Sub-Category. Features, used in connection with the Deacom Product and Sales Configurator, are a group of similar options that may be chosen or configured based on different sales choices.

Search field used to select the Category to which the Sub-Category will be assigned.

• If one Category contains multiple Sub-Categories, a new record will be needed in the Sub-Categories table for each Category/Sub-Category combination.

Displays the name of Sub-Category, which must be unique within one Category.

• The Sub-Category name can be re-used for each Category. Example:

  Category      Sub-Category

  Candies       Chocolate-Covered

  Pretzels       Chocolate-Covered

Stores the planned annual sales in dollars for the selected Sub-Category.

• This field is available for use in the Sales Ranking reports located in Sales > Order Reporting.

If checked, this record is active. Only active records may be used in the system.

Select an appropriate Unit of Measure from the drop down list.

Numeric field used to define the minutes required to receive the Unit of Measure when receiving items in the specified Unit Of Measure that are assigned to this Sub-Category.

If clicked, opens the Edit Feature form and allows the user to select a Feature.

• The Endpoints or sub-Features within the Feature will be available to all items within the Sub-Category, unless overridden at the Item Master level.
• Those overrides can remove Endpoints or sub-Features, but not add them, so all available Endpoints and Features should be defined at the Feature level and subtracted from the Feature tree at the appropriate Category, Sub-Category, or Item Master level.

If clicked, opens the Feature Overrides form, which displays a feature tree of this Sub-Category and all available options and prices, with the capability of overriding pricing and availability. 

• Overrides established at the Category level are in effect at the Sub-Category and Item Master levels, unless overridden at those levels.
• Once an override is modified and saved, the new value from the Sub-Category level will be inherited to the Item Master level.

If clicked, opens the Feature Inclusions form, which displays a list of the inclusions and exclusions that have been added to the current Feature.

Base Unit

Yes

No

No

Yes

No

No

Yes

No

No

Yes

No

No

Yes

No

The name of the Unit of Measure.

Pick list used to define the measurement type. Options are:

• Cube
• Each
• Length
• Volume
• Weight

Defines the conversion factor used by the UOM flagged as "Base Unit" for the same "Type".

• Example: A "Bag - 50lb" UOM with a "Type" of "Weight" would have a "Factor" of "50", representing 50 pounds per one bag.

Defines the time in minutes that it takes to load a "Sales Unit" defined on the Sales Order line.

• Used in connection with the Dock Calendar.
• Example: A tanker truck takes 30 minutes to load at the dock.
• This field provides the default for the "Dock Minutes" (or_dockmins) field on the Edit Sales Order Line General tab.
• Shipment Minutes may also be defined on Item Masters, Categories, and Sub-Categories, allowing companies to define a hierarchy for the minutes that will be required for shipping.
• When specifying Dock Minutes on a Sales Order line, the minutes are based on the "Sales Unit", not the "Stock Unit".

Defines the time in minutes that it takes to unload a "Purchase Unit" defined on the Purchase Order line.

• Used in connection with the Dock Calendar.
• Example: A tanker truck takes 30 minutes to unload while backed into the dock.
• This field provides the default for the "Dock Minutes" (pu_dockmins) field on the Edit Purchase Order Line General tab.
• Receipt Minutes may also be defined on Item Masters, Categories, and Sub-Categories, allowing companies to define a hierarchy for the minutes that will be required for receiving.
• When specifying Dock Minutes on a Purchase Order line, the minutes are based on the "Purchase Unit", not the "Stock Unit".

Pick list required if using the FedEx API used to select the unit that will be used to measure shipments.

• For Each type packages, select "Each".
• The unit selected in this field will also be visible in the "IATA Unit" pick list on the Item Master Calcs tab.

Defines the conversion factor.

• Required if using the FedEx API.
• For Each type packages, use a value of 1.
• Example: If using a UOM of "Box - 10lb", enter a value of 10 in this field.

Defines the standard EDI code used for the Unit of Measure. The most commonly used codes are indicated below. Please note this is not an all inclusive list.

• Bag = BG
• Barrel = BR
• Bottle = BO
• Box = BX
• Bucket = BC
• Can = CN
• Case = CA
• Dozen = DZ
• Drum = DR
• Each = EA
• Fluid Ounce = FO
• Gallon = GA
• Gram = GR
• Keg = KE
• Kilogram = KG
• Liter = LT
• Milliliter = ML
• Ounce Av = OZ
• Package = PK
• Pail = PA
• Pair = PR
• Pallet = PLT
• Pound = LB
• Quart = QT
• Unit = UN
• Note: The stockunitedi, pricunitedi and saleunitedi variables are available to sales order header triggers and sales printouts to represent the EDI codes defined in this field.

If checked, the selected UOM is the base unit for the designated measurement "Type".

• Example: If "Type" is set to "Weight", the base unit would most likely be one pound.

If checked, this record is active. Only active records may be used in the system.

If checked, the selected UOM is used as the default when new Parts are created.

Enter name of vehicle

Name of the Zone, which must be unique. 

Pick list used to select the Facility that the Zone will belong to. Multiple Zones may be assigned to one Facility.

If checked, this record is active. Only active records may be used in the system.

Note: After inactivating Zones, scanner users must log out then back in to Deacom to refresh the Zones list.

If checked, this will be the default Zone on forms throughout the system that contain a "Zone" field. Users may override the default if necessary.